Data transfer policies between source and target servers in a wide area network

ABSTRACT

A computer-implemented method, according to one embodiment, includes: sending a request to a target server to initiate a unidirectional connection, receiving a reply indicating whether the target server is capable of hosting the unidirectional connection or indicating identification of a unidirectional port, initiating a unidirectional connection to the identified unidirectional port of the target server in response to the reply providing the identification of the unidirectional port, sending a request to begin sending data to the target server over the unidirectional connection, receiving a response from the target server indicating that the target server is ready to receive data over the unidirectional connection, sending data to the target server over the unidirectional connection, sending a termination message over the unidirectional connection in response to sending the data to the target server, terminating the unidirectional connection, and performing a next communication with the target server over the TCP/IP connection.

BACKGROUND

The present invention relates to data transfer over networks, and morespecifically, this invention relates to data transfer policies fortransferring data between different locations coupled to a Wide AreaNetwork (WAN).

For a variety of reasons including disaster recovery, computer systemsmay be separated across geographic distances. Establishing and/ormaintaining connectivity between these geographically separated systemsmay include the deployment of WAN technology.

Data storage systems, e.g., WANs, allow for data to be stored inmultiple different storage sites and/or across multiple storage devices.Despite being stored in various locations, all, subsets, some, etc. ofthe data included in a data storage system may be accessed from aplurality of different locations, e.g., terminals. For example, computersystems may be located in different locations which are separated byvarying distances. While this separation allows for disaster recoveryshould one of the computer systems fail, the distance between thecomputer systems has also introduced inefficiency when transferring databetween storage locations. Moreover, these inefficiencies areexacerbated as the amount of data transferred between storage locationsincreases over time.

SUMMARY

A computer-implemented method, according to one embodiment, includes:sending, by a source server, over a TCP/IP connection, a request to atarget server to initiate a unidirectional connection, receiving a replyfrom the target server over the TCP/IP connection, the reply indicatingat least one of: whether the target server is capable of hosting theunidirectional connection and identification of a unidirectional port,in response to the reply indicating that the target server is notcapable of hosting the unidirectional connection, transferring data overthe TCP/IP connection to the target server, initiating a unidirectionalconnection to the identified unidirectional port of the target server inresponse to the reply providing the identification of the unidirectionalport, sending, over the TCP/IP connection, a request to begin sendingdata to the target server over the unidirectional connection, receiving,over the TCP/IP connection, a response from the target server indicatingthat the target server is ready to receive data over the unidirectionalconnection, sending data to the target server over the unidirectionalconnection, sending a termination message over the unidirectionalconnection in response to sending the data to the target server,terminating the unidirectional connection, and performing a nextcommunication with the target server over the TCP/IP connection.

A computer program product, according to another embodiment, includes acomputer readable storage medium having program instructions embodiedtherewith, the program instructions executable by a computer to causethe computer to: send, by the computer, over a TCP/IP connection, arequest to a target server to initiate a unidirectional connection,receive, by the computer, a reply from the target server over the TCP/IPconnection, the reply indicating at least one of: whether the targetserver is capable of hosting the unidirectional connection andidentification of a unidirectional port, in response to the replyindicating that the target server is not capable of hosting theunidirectional connection, transfer, by the computer, data over theTCP/IP connection to the target server, initiate, by the computer, aunidirectional connection to the identified unidirectional port of thetarget server in response to the reply providing the identification ofthe unidirectional port, send, by the computer, over the TCP/IPconnection, a request to begin sending data to the target server overthe unidirectional connection, receive, by the computer, over the TCP/IPconnection, a response from the target server indicating that the targetserver is ready to receive data over the unidirectional connection,send, by the computer, data to the target server over the unidirectionalconnection, send, by the computer, a termination message over theunidirectional connection in response to sending the data to the targetserver, terminate, by the computer, the unidirectional connection, andperform, by the computer, a next communication with the target serverover the TCP/IP connection.

A computer-implemented method, according to yet another embodiment,includes: receiving, by a target server, over a TCP/IP connection, arequest from a source server to initiate a unidirectional connection,sending, from the target server, a reply to the source server over theTCP/IP connection, the reply indicating at least one of: whether thetarget server is capable of hosting the unidirectional connection andidentification of a unidirectional port, in response to sending a replyindicating that the target server is not capable of hosting theunidirectional connection, receiving data over the TCP/IP connectionfrom the source server, initiating a unidirectional connection using theidentified unidirectional port in response to the reply providing theidentification of the unidirectional port, receiving, over the TCP/IPconnection, a request to begin sending data from the source server overthe unidirectional connection, sending, over the TCP/IP connection, aresponse to the source server indicating that the target server is readyto receive data over the unidirectional connection, receiving data fromthe source server over the unidirectional connection, receiving atermination message over the unidirectional connection from the sourceserver after receiving the data, sending, over the TCP/IP connection,acknowledgement of termination of the unidirectional connection to thesource server, and performing a next communication with the sourceserver over the TCP/IP connection.

Other aspects and embodiments of the present invention will becomeapparent from the following detailed description, which, when taken inconjunction with the drawings, illustrate by way of example theprinciples of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network architecture, in accordance with oneembodiment.

FIG. 2 shows a representative hardware environment that may beassociated with the servers and/or clients of FIG. 1, in accordance withone embodiment.

FIG. 3 illustrates a tiered data storage system in accordance with oneembodiment.

FIG. 4A illustrates a flowchart of a method for source server to targetserver data transfer, in accordance with one embodiment.

FIG. 4B illustrates the flowchart of the method of FIG. 4A with switchedserver roles, in accordance with one embodiment.

DETAILED DESCRIPTION

The following description is made for the purpose of illustrating thegeneral principles of the present invention and is not meant to limitthe inventive concepts claimed herein. Further, particular featuresdescribed herein can be used in combination with other describedfeatures in each of the various possible combinations and permutations.

Unless otherwise specifically defined herein, all terms are to be giventheir broadest possible interpretation including meanings implied fromthe specification as well as meanings understood by those skilled in theart and/or as defined in dictionaries, treatises, etc.

It must also be noted that, as used in the specification and theappended claims, the singular forms “a,” “an” and “the” include pluralreferents unless otherwise specified. It will be further understood thatthe terms “comprises” and/or “comprising,” when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

The following description discloses several preferred embodiments ofsystems, methods and computer program products for communication anddata transfer between servers connected to a WAN. Some of theembodiments described herein may establish a data transfer request.

In one general embodiment, a computer-implemented method includes:sending, by a source server, over a TCP/IP connection, a request to atarget server to initiate a unidirectional connection, receiving a replyfrom the target server over the TCP/IP connection, the reply indicatingat least one of: whether the target server is capable of hosting theunidirectional connection and identification of a unidirectional port,in response to the reply indicating that the target server is notcapable of hosting the unidirectional connection, transferring data overthe TCP/IP connection to the target server, initiating a unidirectionalconnection to the identified unidirectional port of the target server inresponse to the reply providing the identification of the unidirectionalport, sending, over the TCP/IP connection, a request to begin sendingdata to the target server over the unidirectional connection, receiving,over the TCP/IP connection, a response from the target server indicatingthat the target server is ready to receive data over the unidirectionalconnection, sending data to the target server over the unidirectionalconnection, sending a termination message over the unidirectionalconnection in response to sending the data to the target server,terminating the unidirectional connection, and performing a nextcommunication with the target server over the TCP/IP connection.

In another general embodiment, a computer program product includes acomputer readable storage medium having program instructions embodiedtherewith, the program instructions executable by a computer to causethe computer to: send, by the computer, over a TCP/IP connection, arequest to a target server to initiate a unidirectional connection,receive, by the computer, a reply from the target server over the TCP/IPconnection, the reply indicating at least one of: whether the targetserver is capable of hosting the unidirectional connection andidentification of a unidirectional port, in response to the replyindicating that the target server is not capable of hosting theunidirectional connection, transfer, by the computer, data over theTCP/IP connection to the target server, initiate, by the computer, aunidirectional connection to the identified unidirectional port of thetarget server in response to the reply providing the identification ofthe unidirectional port, send, by the computer, over the TCP/IPconnection, a request to begin sending data to the target server overthe unidirectional connection, receive, by the computer, over the TCP/IPconnection, a response from the target server indicating that the targetserver is ready to receive data over the unidirectional connection,send, by the computer, data to the target server over the unidirectionalconnection, send, by the computer, a termination message over theunidirectional connection in response to sending the data to the targetserver, terminate, by the computer, the unidirectional connection, andperform, by the computer, a next communication with the target serverover the TCP/IP connection.

In yet another general embodiment, a computer-implemented methodincludes: receiving, by a target server, over a TCP/IP connection, arequest from a source server to initiate a unidirectional connection,sending, from the target server, a reply to the source server over theTCP/IP connection, the reply indicating at least one of: whether thetarget server is capable of hosting the unidirectional connection andidentification of a unidirectional port, in response to sending a replyindicating that the target server is not capable of hosting theunidirectional connection, receiving data over the TCP/IP connectionfrom the source server, initiating a unidirectional connection using theidentified unidirectional port in response to the reply providing theidentification of the unidirectional port, receiving, over the TCP/IPconnection, a request to begin sending data from the source server overthe unidirectional connection, sending, over the TCP/IP connection, aresponse to the source server indicating that the target server is readyto receive data over the unidirectional connection, receiving data fromthe source server over the unidirectional connection, receiving atermination message over the unidirectional connection from the sourceserver after receiving the data, sending, over the TCP/IP connection,acknowledgement of termination of the unidirectional connection to thesource server, and performing a next communication with the sourceserver over the TCP/IP connection.

FIG. 1 illustrates an architecture 100, in accordance with oneembodiment. As shown in FIG. 1, a plurality of remote networks 102 areprovided including a first remote network 104 and a second remotenetwork 106. A gateway 101 may be coupled between the remote networks102 and a proximate network 108. In the context of the presentarchitecture 100, the networks 104, 106 may each take any formincluding, but not limited to a LAN, a WAN such as the Internet, publicswitched telephone network (PSTN), internal telephone network, etc.

In use, the gateway 101 serves as an entrance point from the remotenetworks 102 to the proximate network 108. As such, the gateway 101 mayfunction as a router, which is capable of directing a given packet ofdata that arrives at the gateway 101, and a switch, which furnishes theactual path in and out of the gateway 101 for a given packet.

Further included is at least one data server 114 coupled to theproximate network 108, and which is accessible from the remote networks102 via the gateway 101. It should be noted that the data server(s) 114may include any type of computing device/groupware. Coupled to each dataserver 114 is a plurality of user devices 116. User devices 116 may alsobe connected directly through one of the networks 104, 106, 108. Suchuser devices 116 may include a desktop computer, lap-top computer,hand-held computer, printer or any other type of logic. It should benoted that a user device 111 may also be directly coupled to any of thenetworks, in one embodiment.

A peripheral 120 or series of peripherals 120, e.g., facsimile machines,printers, networked and/or local storage units or systems, etc., may becoupled to one or more of the networks 104, 106, 108. It should be notedthat databases and/or additional components may be utilized with, orintegrated into, any type of network element coupled to the networks104, 106, 108. In the context of the present description, a networkelement may refer to any component of a network.

According to some approaches, methods and systems described herein maybe implemented with and/or on virtual systems and/or systems whichemulate one or more other systems, such as a UNIX system which emulatesan IBM z/OS environment, a UNIX system which virtually hosts a MICROSOFTWINDOWS environment, a MICROSOFT WINDOWS system which emulates an IBMz/OS environment, etc. This virtualization and/or emulation may beenhanced through the use of VMWARE software, in some embodiments.

In more approaches, one or more networks 104, 106, 108, may represent acluster of systems commonly referred to as a “cloud.” In cloudcomputing, shared resources, such as processing power, peripherals,software, data, servers, etc., are provided to any system in the cloudin an on-demand relationship, thereby allowing access and distributionof services across many computing systems. Cloud computing typicallyinvolves an Internet connection between the systems operating in thecloud, but other techniques of connecting the systems may also be used.

FIG. 2 shows a representative hardware environment associated with auser device 116 and/or server 114 of FIG. 1, in accordance with oneembodiment. Such figure illustrates a typical hardware configuration ofa workstation having a central processing unit 210, such as amicroprocessor, and a number of other units interconnected via a systembus 212.

The workstation shown in FIG. 2 includes a Random Access Memory (RAM)214, Read Only Memory (ROM) 216, an I/0 adapter 218 for connectingperipheral devices such as disk storage units 220 to the bus 212, a userinterface adapter 222 for connecting a keyboard 224, a mouse 226, aspeaker 228, a microphone 232, and/or other user interface devices suchas a touch screen and a digital camera (not shown) to the bus 212,communication adapter 234 for connecting the workstation to acommunication network 235 (e.g., a data processing network) and adisplay adapter 236 for connecting the bus 212 to a display device 238.

The workstation may have resident thereon an operating system such asthe Microsoft Windows® Operating System (OS), a MAC OS, a UNIX OS, etc.It will be appreciated that a preferred embodiment may also beimplemented on platforms and operating systems other than thosementioned. A preferred embodiment may be written using XML, C, and/orC++ language, or other programming languages, along with an objectoriented programming methodology. Object oriented programming (OOP),which has become increasingly used to develop complex applications, maybe used.

Now referring to FIG. 3, a storage system 300 is shown according to oneembodiment. Note that some of the elements shown in FIG. 3 may beimplemented as hardware and/or software, according to variousembodiments. The storage system 300 may include a storage system manager312 for communicating with a plurality of media on at least one higherstorage tier 302 and at least one lower storage tier 306. The higherstorage tier(s) 302 preferably may include one or more random accessand/or direct access media 304, such as hard disks in hard disk drives(HDDs), nonvolatile memory (NVM), solid state memory in solid statedrives (SSDs), flash memory, SSD arrays, flash memory arrays, etc.,and/or others noted herein or known in the art. The lower storagetier(s) 306 may preferably include one or more lower performing storagemedia 308, including sequential access media such as magnetic tape intape drives and/or optical media, slower accessing HDDs, sloweraccessing SSDs, etc., and/or others noted herein or known in the art.One or more additional storage tiers 316 may include any combination ofstorage memory media as desired by a designer of the system 300. Also,any of the higher storage tiers 302 and/or the lower storage tiers 306may include some combination of storage devices and/or storage media.

The storage system manager 312 may communicate with the storage media304, 308 on the higher storage tier(s) 302 and lower storage tier(s) 306through a network 310, such as a storage area network (SAN), as shown inFIG. 3, or some other suitable network type. The storage system manager312 may also communicate with one or more host systems (not shown)through a host interface 314, which may or may not be a part of thestorage system manager 312. The storage system manager 312 and/or anyother component of the storage system 300 may be implemented in hardwareand/or software, and may make use of a processor (not shown) forexecuting commands of a type known in the art, such as a centralprocessing unit (CPU), a field programmable gate array (FPGA), anapplication specific integrated circuit (ASIC), etc. Of course, anyarrangement of a storage system may be used, as will be apparent tothose of skill in the art upon reading the present description.

In more embodiments, the storage system 300 may include any number ofdata storage tiers, and may include the same or different storage memorymedia within each storage tier. For example, each data storage tier mayinclude the same type of storage memory media, such as HDDs, SSDs,sequential access media (tape in tape drives, optical disk in opticaldisk drives, etc.), direct access media (CD-ROM, DVD-ROM, etc.), or anycombination of media storage types. In one such configuration, a higherstorage tier 302, may include a majority of SSD storage media forstoring data in a higher performing storage environment, and remainingstorage tiers, including lower storage tier 306 and additional storagetiers 316 may include any combination of SSDs, HDDs, tape drives, etc.,for storing data in a lower performing storage environment. In this way,more frequently accessed data, data having a higher priority, dataneeding to be accessed more quickly, etc., may be stored to the higherstorage tier 302, while data not having one of these attributes may bestored to the additional storage tiers 316, including lower storage tier306. Of course, one of skill in the art, upon reading the presentdescriptions, may devise many other combinations of storage media typesto implement into different storage schemes, according to theembodiments presented herein.

According to some embodiments, the storage system (such as 300) mayinclude logic configured to receive a request to open a data set, logicconfigured to determine if the requested data set is stored to a lowerstorage tier 306 of a tiered data storage system 300 in multipleassociated portions, logic configured to move each associated portion ofthe requested data set to a higher storage tier 302 of the tiered datastorage system 300, and logic configured to assemble the requested dataset on the higher storage tier 302 of the tiered data storage system 300from the associated portions.

Of course, this logic may be implemented as a method on any deviceand/or system or as a computer program product, according to variousembodiments.

Computer systems of a network may be geographically separated from oneanother. Transferring data between these systems in a timely manner maybe difficult because of the performance degradation that may be presentin the network's connectivity. Performance may be limited whentransferring data between systems of the network in response to thenetwork's limited throughput sustainability, high packet loss and/ornetwork latency. For example, when using a conventional storage managerto transmit and/or replicate data over a WAN from one system server toanother, e.g., where the system servers are located at two separatedlocations, the performance characteristics available when usingtransmission control protocol/internet protocol (TCP/IP) over the WANmay prevent the data transfer from completing in a reasonable amount oftime. In response to the TCP/IP anticipating packet loss and latencyissues, these data transfer issues may be further complicated due tothrottling of the workload transfer between the two servers.

User Datagram Protocol (UDP) is a network protocol that has beenconsidered for meeting the rapid data transmission needs between serversdescribed above. However, UDP may not be a desirable data transferprotocol due to UDP sacrificing, e.g., received data reliability,message send/receive acknowledgments, etc., in order to increase datatransfer speeds. Multithreaded storage management program products werealso considered in attempting to meet rapid data transmission needsbetween servers, but were deemed to be provide insufficient high speeddata transfer. This is especially true for a WAN, due to themultithreaded storage management programs contributing to undesirableperformance losses, e.g., bandwidth issues, network congestion, etc.

Dedicated networks and software development kits (SDKs) have also beenconsidered, but similarly promote performance and/or data integrityissues, and thus are not appropriate solutions for meeting rapid datatransmission needs between servers.

In contrast, embodiments described herein use server to serverbi-directional communication capabilities to establish a high speed andreliable unidirectional connection for fast data transfer betweenservers, as will be described in further detail below.

In various embodiments described herein, the TCP/IP connections may beused to send data between a first server (hereinafter a “source server”)and a second server (hereinafter a “target server”) when the data, e.g.,small queries and/or data packets, is determined to be a size that isless than or equal to a predefined threshold. However, it may beundesirable to send data between the source and target servers using theTCP/IP connections when the data is determined to be a size that isgreater than a predefined threshold. The TCP/IP server to serverconnections may be undesirable for transmitting relatively larger datapackets due to resulting latency issues during transmission, the slowertransmission speeds of such connections, losses experienced during thetransmission, etc. However, it should be noted that the size of the datato be transmitted relative to a threshold is in no way intended to limitthe invention. Rather than determining whether a value is greater thanor less than a threshold, equivalent determinations may be made, e.g.,as to whether a value is within a predetermined range, having a valueoutside a predetermined range, having an absolute value above athreshold, etc., depending on the desired approach.

In addition to being used to transfer limited amounts of data betweenservers, the TCP/IP connections may be used to establish aunidirectional connection between the source server and the targetserver for sending data of a size that is greater than a predefinedthreshold. In other words, TCP/IP connections may be used to firstconnect a source and target server, and preferably facilitate thecreation of a unidirectional connection at a desired point in time for abulk data transfer, as will be described in further detail below.

It should be noted that the TCP/IP connection and the unidirectionalconnection may use the same network, e.g., may use a single internetconnection. In other approaches, the unidirectional connection betweenthe source server and the target server may be conducted over adifferent physical connection than the TCP/IP connection, e.g., anauxiliary line or fiber, a second internet connection, etc.

FIG. 4A illustrates how the TCP/IP connection may be used to establish aunidirectional connection and streaming session for sending the datafrom the source server to the target server in accordance with anexemplary embodiment. However, it should be noted that an authenticationof the source server may be performed prior to the implementation ofmethod 400.

In response to the source server having data to be sent to a targetserver, the target server may initiate an authentication of the sourceserver. According to various embodiments, the authentication may occurover existing connections, e.g., existing first communication protocols,between the source server and the target server. For example, theauthentication may occur over one or more existing address familyinternet (AF_INET) TCP/IP socket connections.

Because authentication may be performed over TCP/IP connections betweenservers, it is preferred that the authentication processes may beperformed with a minimal performance footprint. As will be appreciatedby one skilled in the art, TCP/IP connections may degrade as they areused over time. Thus, in an attempt to prevent unnecessary degradationof existing TCP/IP connections between servers of a network, theauthentication process may desirably be performed with minimalperformance impact. This, authentication may be performed regardless ofwhether the process is operating on a degraded network.

The authentication process may also include a transactional setup and/orexchange between the servers. For example, during the authenticationprocess, the two servers may exchange, e.g., over the TCP/IP connection,small amounts of data to establish session connectivity, establish abase communication medium, allow the servers to sign on to TCP/IPconnection between the two servers, etc.

Now referring to FIG. 4A, a flowchart of a method 400 is shown accordingto one embodiment. The method 400 may be performed in accordance withthe present invention in any of the environments depicted in FIGS. 1-3,among others, in various embodiments. Of course, more or less operationsthan those specifically described in FIG. 4A may be included in method400, as would be appreciated by one of skill in the art upon reading thepresent descriptions.

Each of the steps of the method 400 may be performed by any suitablecomponent of the operating environment. For example, in variousembodiments, the method 400 may be partially or entirely performed by acontroller, or some other device having one or more processors therein.The processor, e.g., processing circuit(s), chip(s), and/or module(s)implemented in hardware and/or software, and preferably having at leastone hardware component may be utilized in any device to perform one ormore steps of the method 400. Illustrative processors include, but arenot limited to, a central processing unit (CPU), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA), etc.,combinations thereof, or any other suitable computing device known inthe art.

Method 400 includes data transfer between the source server and thetarget server. The flowchart of the method 400 is illustrated from theperspectives of both the source server and the target server, where thesource server is transmitting data to the target server.

Looking to FIG. 4A, operation 402 of method 400 includes the sourceserver sending a request to a target server to initiate a unidirectionalconnection. The message requesting the unidirectional connection may besent over an established TCP/IP connection, thus the target server mayreceive the request sent by the source server over the TCP/IP connectiontherebetween. According to some approaches, the request to establish aunidirectional connection may be sent in response to the source serverbeing authenticated by the target server as mentioned above. Thus, thesource server may send a request to the target server to initiate aunidirectional connection between the target server and the sourceserver once the source server is authenticated. According to someapproaches, the request sent from the source server to the target servermay include a request to interrogate the target server, e.g., todetermine whether the target is capable of hosting a unidirectionalstream session.

As would be appreciated by one skilled in the art, a unidirectionalconnection may be faster in terms of data transfer rate, e.g., incomparison to a TCP/IP connection. According to various embodiments, anyknown unidirectional protocol may be used to establish theunidirectional connection. According to an illustrative embodiment, theunidirectional connection may be a fast and secure protocol (FASP)connection. To place the description in a context, and by way ofexample, only, the unidirectional connection may be described herein asa FASP connection. In other words, any descriptions and/or examplespresented herein with reference to a FASP connection are in no wayintended to limit the invention, but rather give context in terms of aunidirectional connection. Thus, according to some embodiments, therequest sent from the source server to the target server to initiate aunidirectional connection may include a request for a unidirectionalport, e.g., FASP port identification, as will soon become apparent.

Referring still to method 400, the target server receives the requestfrom the source server to initiate a unidirectional connection inoperation 404, and in response to receiving the request, the targetserver may send one or more replies to the source server, e.g., over theTCP/IP connection. See operation 406. Moreover, operation 408 includesthe source server receiving the reply.

Depending on the embodiment, the one or more replies sent to the sourceserver from the target server may vary, e.g., depending on capabilitiesof the target server. Specifically, the one or more replies from thetarget server may preferably indicate one or more of: whether the targetserver is capable of hosting the unidirectional connection, andidentification of a unidirectional port. Although it is preferred thatthe one or more replies includes an identification of a unidirectionalport, the reply may additionally or alternatively indicate whether thetarget server is capable of hosting the unidirectional connection atall, e.g. in response to an interrogation request from the sourceserver. According to other approaches, the type of reply sent to thesource server from the target server may vary, e.g., depending on thetype of request received. As mentioned above, the request may includeinitiating a unidirectional connection, performing a FASP stream portidentification, interrogating the target server, etc.

In some approaches, the reply sent from the target server to the sourceserver in operation 406 may indicate that the target server is notcapable of hosting the unidirectional connection. Thus, in response toreceiving the reply, the data may be transferred from the source serverto the target server over the TCP/IP connection. Accordingly, the targetserver may receive data over the TCP/IP connection from the sourceserver in response to sending a reply indicating that the target serveris not capable of hosting the unidirectional connection (not shown).This process may server as a failover, and ensure that the data is sentfrom the source server to the target server even when the unidirectionalconnection fails.

According to other embodiments, the data may be sent over the TCP/IPconnection in response to the source server determining that theunidirectional connection cannot be established, e.g., upon experiencinga failed attempting to do so. In such embodiments, transferring the dataover the TCP/IP connection may be performed to avoid data losses, e.g.,due to a loss of signal between the servers during a data transfer.

According to an example, data may be transferred from a source server toa target server over a TCP/IP connection in response to determining thatthe unidirectional connection cannot be established due to occasionalinterrupted signal transmissions on the unidirectional connectionbetween the source server and the target server.

However, according to preferred embodiments, the reply sent from thetarget server to the source server in operation 406 may indicate thatthe target server is capable of hosting the unidirectional connection.Thus, in response to receiving the reply, the source server may send amessage to the target server over the TCP/IP connection, the messagerequesting an identification of a unidirectional port on the targetserver to connect with. See operation 410. In some approaches, thisindication may be made without identifying a unidirectional port on thetarget server to connect with.

In response to receiving the request to identify a unidirectional portas seen in operation 411, the target server preferably sends one or morereplies identifying at least one unidirectional port on the targetserver, e.g., to establish a unidirectional connection with. Seeoperation 412. For example, the target server may send a reply over theTCP/IP connection to the source server, indicating a selected one ormore FASP stream port.

In response to receiving a reply from the target server over the TCP/IPconnection identifying a unidirectional port on the target server (e.g.,in either operation 406 or 412), the source server preferably initiatesa unidirectional connection to the identified unidirectional port of thetarget server. See operation 414. In other words, the source server mayinitiate a unidirectional connection to an identified FASP stream portin response to receiving the reply from the target server. Approacheshaving one or more replies received from the target server may be usedby the source server, (e.g., the source of the data to be transferred),to control whether the data is sent to the target server over theTCIP/IP connection or a unidirectional connection.

When the reply from the target server provides the identification of aunidirectional port, the source server may initiate a unidirectionalconnection, e.g., an outbound unidirectional connection, to theidentified unidirectional port. As will become apparent upon reading thedescriptions herein, the unidirectional port on the target server mayserve as a port for receiving data sent by the source server once aunidirectional connection is established between the source server andthe target server.

The source server may initiate the unidirectional connection to theidentified unidirectional port by, e.g., modifying computer code toinclude the identified unidirectional port as the destination address ofthe unidirectional connection, transmitting a unidirectional connectioninvitation to the target server, initiating the unidirectionalconnection by a process that would be appreciated by one skilled in theart upon reading the present description, etc. The source server mayalso associate the outbound unidirectional connection to the TCP/IPconnection, which may advantageously establish an affinity between theunidirectional connection and the TCP/IP connection.

Moreover, in approaches where the received request to initiate aunidirectional connection also includes a request for a unidirectionalport, the target server may select one, or equivalently multiple portsfor establishing the unidirectional connection. According to oneapproach, the target server may configure such selected ports to accepta connection from the source server. Alternatively, the target servermay not configure such selected ports for accepting a connection fromthe source server and save the configuration of such selected ports fora later initiated connection action, e.g., which may be initiated inresponse to a detection made by a target server listening thread, aswill be described in further detail below.

The target server may mark the one or more of the selectedunidirectional ports as being “in use”, e.g., to ensure that theselected unidirectional port(s) do not become occupied by other targetserver port use requests. It should be noted that components of thesource server and/or the target server may be suspended and subsequentlyresumed and/or be marked “in use” throughout and/or between one or moreof the operations and communication processes described herein. Forexample, the listening threads and ports of the source server and/or thetarget server, may be suspended and subsequently resumed and/or bemarked “in use” between processes, e.g., to reserve such componentsand/or functionalities for specific scheduled data sending tasks. Suchactions may prevent a data sending session from being prematurelyterminated, e.g., which otherwise might occur by a server notrecognizing that a suspended port and/or listening thread was being usedby an active data sending process, e.g., as described in method 400.

Referring still to FIG. 4A, it should be noted that in some approaches,method 400 may skip operations 410 and 412. As mentioned above,operation 406 may actually include the target server indicating aunidirectional port on the target server, e.g., to establish aunidirectional connection with. Thus, operations 410 and 412 may beunnecessary in some approaches.

The target server may also launch a listening thread for a source serverinitiated unidirectional connection which executes asynchronously. Forexample, the target server may launch the listening thread in responseto the target server sending the reply providing the identification ofthe unidirectional port to the source server. According to anotherexample, the target server may launch the listening thread at anypredetermined time and/or in response to any other operation describedherein.

The listening thread may be configured to accept an incomingunidirectional connection, e.g., sent by the source server, on theidentified unidirectional port to configure the unidirectionalconnection and/or accept data sent by the source server to the targetsever over a configured unidirectional connection.

The target server listening thread may also create a unidirectionalconnection session for the identified unidirectional port and associatethe session to the TCP/IP connection session, e.g., to establish anaffinity between the unidirectional connection session and the TCP/IPsession, for data error recovery purposes, to associate a failovercommunication platform in case the unidirectional connection fails, etc.Associating the unidirectional connection session for the identifiedunidirectional port and associate the session to the TCP/IP connectionsession may be especially important in embodiments where the sourceserver sends the data in parallel across multiple unidirectionalconnections to multiple identified unidirectional connection ports onthe target server, e.g., to prevent errors from occurring whenreserializing the data.

Once the unidirectional connection is established, the target serverlistening thread may remain suspended until the unidirectional sessionis no longer in use. For example, the target server listening thread maybe resumed once the data is successfully sent over the unidirectionalconnection, as will be described in greater detail elsewhere herein.

Referring again to the reply from the target server (see operations 406,412), when the reply provides the identification of more than oneunidirectional port, e.g., two unidirectional ports, threeunidirectional ports, any number of unidirectional ports, etc., thesource server initiating the unidirectional connection to the identifiedunidirectional port of the target server may include initiating multipleunidirectional connections with multiple identified unidirectional portsof the target server, where the data is split and sent across themultiple unidirectional connections. In such embodiments, the targetserver initiating the unidirectional connection using the identifiedunidirectional port of the target server may include initiating multipleunidirectional connections using multiple identified unidirectionalports of the target server, where the data is received across themultiple unidirectional connections.

Sending the data across multiple unidirectional connections between thesource server and the target server may desirably decrease thetransmission time of sending the data from the source server to thetarget server, e.g., due to each unidirectional connection sending onlya portion of the total data.

Referring still to method 400, operation 416 further includes using theTCP/IP connection to send a request to begin sending data to the targetserver over the unidirectional connection. In other words, the sourceserver may send, over the TCP/IP connection, a request to begin sendingdata to the target server over the unidirectional connection. Therequest to begin sending data to the target server over the newunidirectional connection may be sent by the source server to bring thetarget server's listening thread out of a suspended state and/or ensurethat the unidirectional connection is still established. Although theunidirectional connection may at least be initiated (e.g., established),the target server may not be ready to receive data over theunidirectional connection. Thus, a request may be used to confirm thestatus of the target server.

In response to receiving the request to begin sending data from thesource server over the unidirectional connection as seen in operation418, the target server may evaluate whether it is ready to receive datafrom the source server over the unidirectional connection. Whenappropriate, the target server may generate and send a response to thesource server over the TCP/IP connection, indicating that the targetserver is ready to receive data over the unidirectional connection. Seeoperation 420. It should be noted that upon sending the response to thesource server, the target server may be ready to receive data from thesource server. For example, prior to the notifying the source serverthat the target server is ready to receive data over the FASP stream,the target server may block any data from being received over the FASPconnection. Accordingly, upon notifying the source server that thetarget server is ready to receive data over the FASP stream, the targetserver may no longer block data from being received over the FASPconnection. Thus, the target may not issue a blocking call to incomingsource server connections subsequent to the sending of the response toreceive data from the source server.

The target server may also send, over the TCP/IP connection, a securitytoken to the source server, where the security token is sent with therequest to begin sending data to the target server over theunidirectional connection to validate the source server. For example,the security token may include, e.g., a predefined binary bit sequence,a security token preset and recognized by the source server as well asthe target server, a security token of a type known in the art, etc. Thesecurity token may ensure that the data transmission between the sourceserver and the target server is secure, e.g., not mistakenlyshared/addressed to other linked servers in the WAN.

According to further embodiments, the security token may be sent fromthe target server to the source server along with the identifiedunidirectional connection port (see operation 412 above).

The target server may set a flag in a TCP session associated with theTCP/IP connection that the next inbound data is to be received over theunidirectional connection in response to sending the response to thesource server indicating that the target server is ready to receive dataover the unidirectional connection. The flag set by the target servermay ensure that the target is prepared to receive and/or listening forthe data sending on the unidirectional connection and not the TCP/IPconnection.

Furthermore, operation 422 includes the source server receiving theresponse from the target server indicating that the target server isready to receive data over the unidirectional connection. In response toreceiving the reply from the target server indicating that the targetserver is ready to receive data over the unidirectional connection, thesource server may mark/queue data for sending over the unidirectionalconnection. According to some approaches, the source server may alsoreceive (over the TCP/IP connection) the security token from the targetserver. The security token may be received with the request to beginsending data to the target server over the unidirectional connection tovalidate the source server.

The source server may set a flag in a TCP session associated with theTCP/IP connection that the next outbound data send request is to be sentover the unidirectional connection in response to receiving the responsefrom the target server indicating that the target server is ready toreceive data over the unidirectional connection. The flag may suspendthe TCP session, for future bi-lateral communication between the sourceserver and target server, e.g. after a termination of the unidirectionalconnection.

In response to the target server indicating that the target server isready to receive data over the unidirectional connection, the targetserver may send data to the target server over the unidirectionalconnection. Accordingly, operation 424 includes sending data from thesource server to the target server over the unidirectional connection,while operation 426 includes the target server receiving data from thesource server over the unidirectional connection, as shown.

According to various embodiments, the target server may send the data tothe target server over the unidirectional connection as a continuousdata stream until all the data has been transferred to the targetserver. In other embodiments, the target server may send the data to thetarget server over the unidirectional connection in one or more datapackets until all the data has been transferred to the target server.Accordingly, the source server may continue to send the data until allof the data has been sent to the target server.

As previously described, sending the data to the target server over theunidirectional connection may provide a highly productive transfer ofdata from the source server to the target server due to the high speedsending capabilities of the unidirectional connection, and maintainedintegrity of the sent data.

In response to receiving data from the source server over theunidirectional connection, the target server may then, e.g., store thereceived data, reconfigure the data in response to the data beingreceived in more than one data packet, reserialize the data received atmore than one identified unidirectional port in response to the databeing split and sent in parallel across multiple unidirectionalconnections by the source server, etc.

According to some embodiments, the source server may probe networkperformance during the sending the data to the target server over theunidirectional connection. The probing may be used to determine if usingthe unidirectional connection to send data to the target server is morepreferable, e.g. faster, more reliable, more efficient, etc., thansending the data over the TCP/IP connection. As network characteristicschange over time, with use, etc., the TCP/IP connection and/or othertypes of connection between the source and target servers may be morepreferable, e.g., in terms of the efficiency resulting from theirimplementation.

The source server may apply a preset policy in response to the probingindicating that a network performance characteristic meets a given oneor more criterion, which may be predetermined, calculated in real time,set by a user, etc. Applying a policy may preferably include the sourceserver switching the connection that the data is sent from the sourceserver to the target server over, e.g., in response to the probingindicating that the currently used connection not performing inaccordance with the performance criterion. According to one approach,applying the policy may include changing the data transfer to the TCP/IPconnection, e.g., from the unidirectional connection, in response to theprobing indicating that sending data over the unidirectional connectionis less efficient than sending the data over the TCP/IP connection wouldprovide. However, according to further approaches, the source server mayswitch the connection that the data is sent from the source server tothe target server over for any desired reason.

The target server may also probe network performance during thereceiving the data from the source server over the unidirectionalconnection and apply a preset policy in response to the probingindicating that a network performance characteristic meets a given oneor more criterion.

At some point, a termination message may be created (e.g., built) andsent over the unidirectional connection, e.g., in response tosuccessfully sending all of the data to the target server. See operation428. Moreover, operation 430 includes receiving the termination messageat the target server. According to one illustrative embodiment, thetermination message may include a “stop using FASP” message to indicatethat the FASP session is no longer needed, e.g., no longer needed forcurrent data sending but alternatively may be suspended and used forsubsequent data sending. According to further embodiments, thetermination request may be generated and scheduled for sending by thesource server at a desired time.

According to another approach, the termination message may be generatedand sent by the source server to the target server with data over theunidirectional connection in response to determining that data sendingis close to being complete. In such an approach, the termination messagemay include a notification of a characteristic that the last portion ofdata being sent over the unidirectional connection includes.Accordingly, upon receiving the data with the identified characteristic,the target server may determine that it has received all of the datasent by the source server over the unidirectional connection.

In one approach, the termination message may be sent after all data hasbeen transferred between the source and target servers. According toother approaches, the termination message may be sent after an amount oftime has passed, after a predetermined amount of processing power hasbeen expended, after an amount of data has been transferred, etc.

Once a termination message has been received at the target server,preparations may be made at the source and/or target servers with regardto future operations. For example, the source server may mark futuredata transfers to be sent over the TCP/IP connection.

Referring still to FIG. 4A, operation 432 includes terminating theunidirectional connection. According to one approach, the source servermay terminate the unidirectional connection, e.g., at least aftersending the termination message to the target server. Additionally oralternatively, the target server may terminate the unidirectionalconnection.

According to one approach, the source server may unset the flag set inthe TCP session, e.g., due to the unidirectional session being no longerin use after the termination message was sent to the target server, andwait for a response by the target server on the TCP/IP session. Thesource server may unset the flag in the TCP session in conjunction withsending the termination message.

The source server may terminate the unidirectional connection byunsetting the suspended source server flag that was previously suspendedafter the unidirectional connection was established. Unsetting thesource server flag may indicate that the unidirectional connectionsession is no longer in use, and resume the bi-directional TCP/IPsession between the source server and the target server.

The target server may receive the termination message over theunidirectional connection in response to receiving the data from thesource server. In response to receiving the termination message, thetarget server may mark the unidirectional stream as unavailable and/orterminate the unidirectional connection. For example, after receivingthe termination message, the target server may mark the FASP stream as“unavailable” and terminate the FASP stream.

The target server may terminate the unidirectional connection, e.g. inresponse to receiving the termination message from the source server.For example, the target server may unset the flag set in the associatedTCP session, e.g., to reflect that the target server will no longer beusing the unidirectional session, in response to receiving thetermination message from the source server. The target server may alsosignal the suspended target server listening thread, e.g., to resume thesuspended listening thread. In response to the target server unsettingthe flag set in the associated TCP/IP session, and signaling thesuspended listening thread, the listening thread may be returned to aresumed state. With the listening thread resumed and TCP/IP connectionresumed, the unidirectional session may be terminated, and the targetserver identified unidirectional port may be returned to the “available”state, e.g., relinquishing use of the port.

The target server may send over the TCP/IP connection, acknowledgementof termination of the unidirectional connection to the source server.For example, referring again to method 400, operation 434 includes thetarget server sending acknowledgement to the source server over TCP/IPconnection, indicating that the unidirectional connection to the sourceserver has been terminated. In other words, a FASP connection betweenthe source and target servers is no longer available.

According various embodiments, the termination acknowledgement mayinclude a reference code that may be used to subsequently re-establishthe unidirectional connection. According to one approach the referencecode may re-establish the unidirectional connection in response to thesource server having data to be sent to the target server, and thepreviously used unidirectional connection port and/or a similarunidirectional connection port being available.

Although the source server has been described elsewhere herein toterminate the unidirectional connection in conjunction with the sourceserver sending the termination message to the target server, accordingto other embodiments, the source server may terminate the unidirectionalconnection and/or session in response to receiving the terminationconfirmation message from the target server. For example, operation 430of method 400 above includes the source server terminating the FASPstream in response to receiving the termination message acknowledgmentfrom the target server.

In response to each server determining that the unidirectionalconnection has been terminated, the source server and the target servermay perform a next communication with the each other over the TCP/IPconnection.

Because the unidirectional connection between the source server andtarget server has been terminated, next (subsequent) communicationsbetween the two servers may be performed over the TCP/IP connectiontherebetween. For example, the TCP/IP connection between the sourceserver and target server may be used to establish another unidirectionalconnection, e.g., by performing method 400 again. According to someapproaches, a termination message may be issued which includes anotification that the next communication and/or data will be sent fromthe source server to the target server over the TCP/IP connection and/ora request to termination of the FASP stream.

FIG. 4B illustrates data transfer in the reverse direction, where thetarget server sends data to the source server over a unidirectionalconnection.

Referring to FIG. 4B, a flowchart of a method 450 is shown according toone embodiment. The method 450 may be performed in accordance with thepresent invention in any of the environments depicted in FIGS. 1-4A,among others, in various embodiments. Of course, more or less operationsthan those specifically described in FIG. 4B may be included in method450, as would be appreciated by one of skill in the art upon reading thepresent descriptions.

Each of the steps of the method 450 may be performed by any suitablecomponent of the operating environment. For example, in variousembodiments, the method 450 may be partially or entirely performed by acontroller, or some other device having one or more processors therein.The processor, e.g., processing circuit(s), chip(s), and/or module(s)implemented in hardware and/or software, and preferably having at leastone hardware component may be utilized in any device to perform one ormore steps of the method 450. Illustrative processors include, but arenot limited to, a central processing unit (CPU), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA), etc.,combinations thereof, or any other suitable computing device known inthe art.

The operations of FIG. 4B mirror the operations of method 400 of FIG.4A, but with switched server roles. Each of the operations performed bythe source server in method 400 of FIG. 4A are shown performed by thetarget server in method 450 of FIG. 4B, and each of the operationsperformed by the target server in method 400 of FIG. 4A are shownperformed by the source server in method 450 of FIG. 4B. Accordingly,the operations of FIG. 4B have common numbering with those of FIG. 4A.Accordingly, the target server of the WAN may send data to the sourceserver of the WAN for the advantageous purposes described elsewhereherein.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

Moreover, a system according to various embodiments may include aprocessor and logic integrated with and/or executable by the processor,the logic being configured to perform one or more of the process stepsrecited herein. By integrated with, what is meant is that the processorhas logic embedded therewith as hardware logic, such as an applicationspecific integrated circuit (ASIC), a FPGA, etc. By executable by theprocessor, what is meant is that the logic is hardware logic; softwarelogic such as firmware, part of an operating system, part of anapplication program; etc., or some combination of hardware and softwarelogic that is accessible by the processor and configured to cause theprocessor to perform some functionality upon execution by the processor.Software logic may be stored on local and/or remote memory of any memorytype, as known in the art. Any processor known in the art may be used,such as a software processor module and/or a hardware processor such asan ASIC, a FPGA, a central processing unit (CPU), an integrated circuit(IC), a graphics processing unit (GPU), etc.

It will be clear that the various features of the foregoing systemsand/or methodologies may be combined in any way, creating a plurality ofcombinations from the descriptions presented above.

It will be further appreciated that embodiments of the present inventionmay be provided in the form of a service deployed on behalf of acustomer to offer service on demand.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation.

Thus, the breadth and scope of a preferred embodiment should not belimited by any of the above-described exemplary embodiments, but shouldbe defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A computer-implemented method, comprising:sending, by a source server, over a TCP/IP connection, a request to atarget server to initiate a unidirectional connection; receiving a replyfrom the target server over the TCP/IP connection, the reply indicatingat least one of: whether the target server is capable of hosting theunidirectional connection and identification of a unidirectional port;in response to the reply indicating that the target server is notcapable of hosting the unidirectional connection, transferring data overthe TCP/IP connection to the target server; initiating a unidirectionalconnection to the identified unidirectional port of the target server inresponse to the reply providing the identification of the unidirectionalport; sending, over the TCP/IP connection, a request to begin sendingdata to the target server over the unidirectional connection; receiving,over the TCP/IP connection, a response from the target server indicatingthat the target server is ready to receive data over the unidirectionalconnection; sending data to the target server over the unidirectionalconnection; sending a termination message over the unidirectionalconnection in response to sending the data to the target server;terminating the unidirectional connection; and performing a nextcommunication with the target server over the TCP/IP connection.
 2. Thecomputer-implemented method of claim 1, wherein the unidirectionalconnection is a fast and secure protocol (FASP) connection.
 3. Thecomputer-implemented method of claim 1, comprising probing networkperformance during the sending the data to the target server over theunidirectional connection, applying a preset policy in response to theprobing indicating that a network performance characteristic meets apredetermined criterion, wherein applying the policy includes changingthe data transfer to the TCP/IP connection.
 4. The computer-implementedmethod of claim 1, comprising setting a flag in a TCP session associatedwith the TCP/IP connection that a next outbound data send request is tobe sent over the unidirectional connection in response to receiving theresponse from the target server indicating that the target server isready to receive data over the unidirectional connection, and unsettingthe flag in the TCP session in conjunction with sending the terminationmessage.
 5. The computer-implemented method of claim 1, wherein asecurity token is received from the target server, wherein the securitytoken is sent with the request to begin sending data to the targetserver over the unidirectional connection to validate the source server.6. The computer-implemented method of claim 1, wherein initiating theunidirectional connection to the identified unidirectional port of thetarget server includes initiating multiple unidirectional connectionswith multiple identified unidirectional ports of the target server,wherein the data is split and sent across the multiple unidirectionalconnections.
 7. The computer-implemented method of claim 1, wherein thedata is sent over the TCP/IP connection in response to determining thatthe unidirectional connection cannot be established upon attempting toestablish the unidirectional connection.
 8. A computer program product,the computer program product comprising a computer readable storagemedium having program instructions embodied therewith, the programinstructions executable by a computer to cause the computer to: send, bythe computer, over a TCP/IP connection, a request to a target server toinitiate a unidirectional connection; receive, by the computer, a replyfrom the target server over the TCP/IP connection, the reply indicatingat least one of: whether the target server is capable of hosting theunidirectional connection and identification of a unidirectional port;in response to the reply indicating that the target server is notcapable of hosting the unidirectional connection, transfer, by thecomputer, data over the TCP/IP connection to the target server;initiate, by the computer, a unidirectional connection to the identifiedunidirectional port of the target server in response to the replyproviding the identification of the unidirectional port; send, by thecomputer, over the TCP/IP connection, a request to begin sending data tothe target server over the unidirectional connection; receive, by thecomputer, over the TCP/IP connection, a response from the target serverindicating that the target server is ready to receive data over theunidirectional connection; send, by the computer, data to the targetserver over the unidirectional connection; send, by the computer, atermination message over the unidirectional connection in response tosending the data to the target server; terminate, by the computer, theunidirectional connection; and perform, by the computer, a nextcommunication with the target server over the TCP/IP connection.
 9. Thecomputer program product of claim 8, wherein the unidirectionalconnection is a fast and secure protocol (FASP) connection.
 10. Thecomputer program product of claim 8, comprising program instructionsexecutable by a computer to cause the computer to probe networkperformance during the sending the data to the target server over theunidirectional connection, and apply a preset policy in response to theprobing indicating that a network performance characteristic meets apredetermined criterion, wherein applying the policy includes changingthe sending of the data to the TCP/IP connection.
 11. The computerprogram product of claim 8, comprising program instructions executableby a computer to cause the computer to set a flag in a TCP sessionassociated with the TCP/IP connection that a next outbound data sendrequest is to be sent over the unidirectional connection in response toreceiving the response from the target server indicating that the targetserver is ready to receive data over the unidirectional connection, andunset the flag in the TCP session in conjunction with sending thetermination message.
 12. The computer program product of claim 8,wherein a security token is received from the target server, wherein thesecurity token is sent with the request to begin sending data to thetarget server over the unidirectional connection to validate a sourceserver,
 13. The computer program product of claim 8, wherein initiatingthe unidirectional connection to the identified unidirectional port ofthe target server includes initiating multiple unidirectionalconnections with multiple identified unidirectional ports of the targetserver, wherein the data is split and sent across the multipleunidirectional connections.
 14. The computer program product of claim 8,wherein the data is sent over the TCP/IP connection in response todetermining that the unidirectional connection cannot be establishedupon attempting to establish the unidirectional connection.
 15. Acomputer-implemented method, comprising: receiving, by a target server,over a TCP/IP connection, a request from a source server to initiate aunidirectional connection; sending, from the target server, a reply tothe source server over the TCP/IP connection, the reply indicating atleast one of: whether the target server is capable of hosting theunidirectional connection and identification of a unidirectional port;in response to sending a reply indicating that the target server is notcapable of hosting the unidirectional connection, receiving data overthe TCP/IP connection from the source server; initiating aunidirectional connection using the identified unidirectional port inresponse to the reply providing the identification of the unidirectionalport; receiving, over the TCP/IP connection, a request to begin sendingdata from the source server over the unidirectional connection; sending,over the TCP/IP connection, a response to the source server indicatingthat the target server is ready to receive data over the unidirectionalconnection; receiving data from the source server over theunidirectional connection; receiving a termination message over theunidirectional connection from the source server after receiving thedata; sending, over the TCP/IP connection, acknowledgement oftermination of the unidirectional connection to the source server; andperforming a next communication with the source server over the TCP/IPconnection.
 16. The computer-implemented method of claim 15, wherein theunidirectional connection is a fast and secure protocol (FASP)connection.
 17. The computer-implemented method of claim 15, comprisingprobing network performance during the receiving the data from thesource server over the unidirectional connection, applying a presetpolicy in response to the probing indicating that a network performancecharacteristic meets a predetermined criterion, wherein applying thepolicy includes changing the sending of the data to the TCP/IPconnection.
 18. The computer-implemented method of claim 15, comprisingsetting a flag in a TCP session associated with the TCP/IP connectionthat a next inbound data is to be received over the unidirectionalconnection in response to sending the response to the source serverindicating that the target server is ready to receive data over theunidirectional connection, and unsetting the flag in the TCP session inresponse to receiving the termination message.
 19. Thecomputer-implemented method of claim 15, comprising sending a securitytoken to the source server, wherein the security token is sent with therequest to begin sending data to the target server over theunidirectional connection to validate the source server.
 20. Thecomputer-implemented method of claim 15, wherein initiating theunidirectional connection using the identified unidirectional port ofthe target server includes initiating multiple unidirectionalconnections using multiple identified unidirectional ports of the targetserver, wherein the data is received across the multiple unidirectionalconnections.